Dynamic user interface generation for delivery scheduling optimization

ABSTRACT

A system for generating dynamic user interfaces includes memory hardware storing instructions and processor hardware executing the instructions. The instructions include generating an interactive graphical user interface with fields corresponding to dates. The instructions include generating a selectable user interface element at a first field corresponding to a scheduled delivery date for a recipient. The instructions include, in response to a user dragging-and-dropping the selectable user interface element to a second field corresponding to an adjusted delivery date for the recipient, calculating a supply measure of a prior fill remaining with the recipient based on a stated duration of the prior fill and a date indicating receipt of the prior fill by the recipient. The instructions include, in response to the supply measure being greater than the threshold, moving the selectable user interface element to the second field and updating the scheduled delivery date to be the adjusted delivery date.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. Pat. Application No.16/449,317 filed Jun. 21, 2019 (now U.S. Pat. No. 11,515,023), theentire disclosure of which is incorporated by reference.

FIELD

The present disclosure relates to computerized graphical user interfacesand, more particularly, to calendar-based graphical user interfaces.

BACKGROUND

Currently, entities such as high-volume pharmacies offer online drugmanagement programs. For example, a user who is a member of a pharmacycan create an account using a user device to access the drug managementprogram. Each user may be able to access their information and may bepresented with a user interface illustrating their prescription historyand/or insurance information. Users may be able to request drug refillsand review delivery information.

The background description provided here is for the purpose of generallypresenting the context of the disclosure. Work of the presently namedinventors, to the extent it is described in this background section, aswell as aspects of the description that may not otherwise qualify asprior art at the time of filing, are neither expressly nor impliedlyadmitted as prior art against the present disclosure.

SUMMARY

A delivery scheduling method includes receiving a bundle request from auser and identifying a first prescription scheduled for delivery withina first date range. The method includes setting a scheduled deliverydate of the first prescription as a target delivery date and identifyinga set of prescriptions scheduled for delivery within a predeterminedtime of the target delivery date. The method includes selecting one ofthe set of prescriptions as a candidate prescription and obtainingprescription parameters of the candidate prescription including a priorfill date of the candidate prescription. The method includes determininga required fill date of the candidate prescription. The required filldate is a latest fill date of the candidate prescription to deliver thecandidate prescription by the target delivery date. The method includesdetermining a blackout window for the candidate prescription based on apredetermined window following a prior fill date of the candidateprescription and, in response to the required fill date being after theblackout window, adjusting a delivery date of the candidate prescriptionto the target delivery date.

In other features, the first date range encompasses a predeterminedperiod of time following a present date on which the bundle request ismade. In other features, the method includes, in response to therequired fill date being within the blackout window, updating the targetdelivery date by determining an earliest fill date of the candidateprescription following the blackout window and determining an earliestdelivery date of the candidate prescription based on the earliest filldate of the candidate prescription. Updating the target delivery datealso includes setting the target delivery date to the earliest deliverydate. The method includes repeating the selecting, obtaining,determining, adjusting, and updating steps. In other features, themethod includes adding each prescription scheduled for delivery withinthe predetermined time of the target delivery date to a bundle list and,for each prescription in the bundle list, setting the prescription inthe bundle list as the candidate prescription and performing theselecting, obtaining, determining, adjusting, and updating steps.

In other features, the method includes, in response to the delivery dateof the candidate prescription being earlier than the target deliverydate, determining a days supply on hand of the candidate prescriptionfor the user as of the target delivery date and, in response to the dayssupply on hand being less than a first threshold, removing the candidateprescription from the bundle list. In other features, the methodincludes, in response to the days supply on hand being greater than thefirst threshold but less than a second threshold, generating an alertindicating the days supply on hand is below the second threshold andselectively transmitting the alert to the user. In other features, themethod includes, in response to the candidate prescription being arefill prescription, performing the determining the blackout window. Inother features, the method includes, in response to the candidateprescription being a new prescription not having been filled before,skipping determining the blackout window with respect to the candidateprescription.

In other features, the method includes, in response to a schedulingrequest for a new prescription, scheduling the new prescription fordelivery by obtaining prescription parameters of the new prescription.In other features, scheduling the new prescription for delivery furtherincludes, in response to a requested delivery date not being specifiedfor the new prescription, determining an earliest fill date of the newprescription, determining an earliest delivery date of the newprescription based on the earliest fill date and delivery time, andsetting a delivery date of the new prescription to the earliest deliverydate.

In other features, scheduling the new prescription for delivery furtherincludes, in response to the requested delivery date being specified forthe new prescription, determining the earliest fill date of the newprescription and determining a requested fill date of the newprescription based on the requested delivery date of the newprescription. The method further includes, in response to the requestedfill date being later than the earliest fill date, setting the deliverydate of the new prescription to the requested delivery date. The methodfurther includes, in response to the requested fill date being earlierthan the earliest fill date, determining the earliest delivery date ofthe new prescription based on the earliest fill date and setting thedelivery date of the new prescription to the earliest delivery date.

In other features, the prescription parameters include a prescribingphysician, a drug identification, a drug dosage, a name of the user, andan address of the user. In other features, the prescription parametersof the candidate prescription include the prior fill date of thecandidate prescription in response to the prescription parametersindicating the candidate prescription is a refill.

A delivery scheduling system includes at least one processor and amemory storing instructions for execution on the at least one processor.The instructions, upon execution, cause the at least one processor toreceive a bundle request from a user, identify a first prescriptionscheduled for delivery within a first date range, and set a scheduleddelivery date of the first prescription as a target delivery date. Theinstructions, upon execution, further cause the at least one processorto identify a set of prescriptions scheduled for delivery within apredetermined time of the target delivery date, select one of the set ofprescriptions as a candidate prescription, and obtain prescriptionparameters of the candidate prescription including a prior fill date ofthe candidate prescription. The instructions, upon execution, furthercause the at least one processor to determine a required fill date ofthe candidate prescription. The required fill date is a latest fill dateof the candidate prescription to deliver the candidate prescription bythe target delivery date. The instructions, upon execution, furthercause the at least one processor to determine a blackout window for thecandidate prescription based on a predetermined window following a priorfill date of the candidate prescription and, in response to the requiredfill date being after the blackout window, adjust a delivery date of thecandidate prescription to the target delivery date

In other features, the first date range encompasses a predeterminedperiod of time following a present date on which the bundle request ismade. In other features, the instructions, upon execution, cause the atleast one processor to, in response to the required fill date beingwithin the blackout window, update the target delivery date bydetermining an earliest fill date of the candidate prescriptionfollowing the blackout window, determining an earliest delivery date ofthe candidate prescription based on the earliest fill date of thecandidate prescription, and setting the target delivery date to theearliest delivery date. The method includes repeating the select,obtain, determine, adjust, and update steps.

In other features, the instructions, upon execution, cause the at leastone processor to add each prescription scheduled for delivery within thepredetermined time of the target delivery date to a bundle list and, foreach prescription in the bundle list, set the prescription in the bundlelist as the candidate prescription and perform the select, obtain,determine, adjust, and update steps. In other features, theinstructions, upon execution, cause the at least one processor to, inresponse to the delivery date of the candidate prescription beingearlier than the target delivery date, determine a days supply on handof the candidate prescription for the user as of the target deliverydate and, in response to the days supply on hand being less than a firstthreshold, remove the candidate prescription from the bundle list.

In other features, the instructions, upon execution, cause the at leastone processor to, in response to the days supply on hand being greaterthan the first threshold but less than a second threshold, generate analert indicating the days supply on hand is below the second thresholdand selectively transmit the alert to the user.

In other features, the instructions, upon execution, cause the at leastone processor to, in response to a scheduling request for a newprescription, schedule the new prescription for delivery by obtainingprescription parameters of the new prescription and, in response to arequested delivery date not being specified for the new prescription,determining an earliest fill date of the new prescription, determiningan earliest delivery date of the new prescription based on the earliestfill date and delivery time, and setting a delivery date of the newprescription to the earliest delivery date.

In other features, scheduling the new prescription for delivery furtherincludes, in response to the requested delivery date being specified forthe new prescription, determining the earliest fill date of the newprescription and determining a requested fill date of the newprescription based on the requested delivery date of the newprescription. In other features, scheduling the new prescription fordelivery further includes, in response to the requested fill date beinglater than the earliest fill date, setting the delivery date of the newprescription to the requested delivery date and, in response to therequested fill date being earlier than the earliest fill date,determining the earliest delivery date of the new prescription based onthe earliest fill date and setting the delivery date of the newprescription to the earliest delivery date.

A non-transitory computer-readable medium stores processor-executableinstructions. The instructions include receiving a bundle request from auser and identifying a first prescription scheduled for delivery withina first date range. The instructions further include setting a scheduleddelivery date of the first prescription as a target delivery date andidentifying a set of prescriptions scheduled for delivery within apredetermined time of the target delivery date. The instructions furtherinclude selecting one of the set of prescriptions as a candidateprescription and obtaining prescription parameters of the candidateprescription including a prior fill date of the candidate prescription.The instructions further include determining a required fill date of thecandidate prescription. The required fill date is a latest fill date ofthe candidate prescription to deliver the candidate prescription by thetarget delivery date. The instructions further include determining ablackout window for the candidate prescription based on a predeterminedwindow following a prior fill date of the candidate prescription and, inresponse to the required fill date being after the blackout window,adjusting a delivery date of the candidate prescription to the targetdelivery date.

Further areas of applicability of the present disclosure will becomeapparent from the detailed description, the claims, and the drawings.The detailed description and specific examples are intended for purposesof illustration only and are not intended to limit the scope of thedisclosure.

BRIEF DESCRIPTION OF THE DRAWINGS

The present disclosure will become more fully understood from thedetailed description and the accompanying drawings.

FIG. 1 is a functional block diagram of an example system including ahigh-volume pharmacy.

FIG. 2 is a functional block diagram of an example pharmacy fulfillmentdevice, which may be deployed within the system of FIG. 1 .

FIG. 3 is a functional block diagram of an example order processingdevice, which may be deployed within the system of FIG. 1 .

FIGS. 4A-4B together are an example prescription delivery schedulinginterface depicting a calendar view of scheduled deliveries ofprescription drugs.

FIGS. 5A-5B together are an example prescription delivery schedulinginterface depicting a calendar view of a selected prescription drugscheduled for delivery.

FIGS. 6A-6B together are an example prescription delivery schedulinginterface depicting a calendar view of scheduled deliveries ofprescription drugs with bundled delivery dates.

FIGS. 7A-7B together are an example prescription delivery schedulinginterface depicting a calendar view of scheduled deliveries including aprescription that is being processed resulting in a rescheduling of thedelivery of the prescription not being guaranteed.

FIGS. 8A-8B together are an example prescription delivery schedulinginterface depicting blocking out dates that are too soon to refill aprescription when a user is performing a drag operation.

FIGS. 9A-9B together are an example prescription delivery schedulinginterface depicting a calendar view of scheduled deliveries confirming arescheduled delivery.

FIG. 10 is a functional block diagram of an example implementation of aprescription delivery scheduling device.

FIG. 11 is a flowchart of example operation of a prescription deliverydate scheduling interface.

FIG. 12 is a flowchart of example delivery date block-out.

FIGS. 13A-13B together are a flowchart of example operation of automatedprescription delivery date bundling.

In the drawings, reference numbers may be reused to identify similarand/or identical elements.

DETAILED DESCRIPTION

A prescription delivery scheduling device offers an interactive userinterface where user-guided automation can adjust scheduled prescriptiondelivery dates according to user preferences. The prescription deliveryscheduling device controls a prescription delivery calendar, accessibleusing a web portal, that displays a calendar view of scheduled deliverydates of each of the user’s prescriptions. In various implementations,the user creates login credentials through their pharmacy, pharmacybenefit manager (PBM), insurance provider, etc., to access apersonalized user account.

Through the personalized user account, the user can access theirprescription delivery calendar and adjust scheduled prescriptiondelivery dates. The prescription delivery calendar may includeprescriptions of all individuals listed on the insurance of the user. Invarious implementations, the user can designate which individuals areincluded on the user’s prescription delivery calendar. The user may beable to delegate access to or control of their prescription deliverycalendar. For example, the user may delegate access to theirprescription delivery calendar to a caregiver on a separate insuranceplan. Additionally, the user can designate access to their prescriptiondelivery calendar to a facility, such as an assisted living facility,hospital, etc. In various implementations, the prescription deliverycalendar may be filtered according to the prescription type, patientidentity, date range, etc.

The user may adjust a delivery date of a scheduled prescription using adrag-and-drop operation. The prescription delivery scheduling device mayreceive a delivery date adjustment request, such as the initiation of adrag-and-drop operation by the user, and may determine whether thedelivery date of the scheduled prescription can be updated to arequested delivery date.

The prescription delivery scheduling device considers the capacity of apharmacy assigned to fill the scheduled prescription to determine anearliest possible fill date of the scheduled prescription. The earliestpossible fill date of the scheduled prescription will determine theearliest possible delivery date of the prescription. Therefore, ininstances of the user attempting to adjust the delivery date of thescheduled prescription to an earlier date, the prescription deliveryscheduling device may calculate whether the assigned pharmacy is capableof fulfilling an order in time to make the requested delivery date.

In various implementations, for a refill prescription, the prescriptiondelivery scheduling device also considers a measure of how much of theprior prescription remains with the user. For example, a measure calleddays supply on hand (DSOH) indicates how many days — assuming the userfollowed the previously-prescribed dosing regimen — of the prescriptionremain with the user on a certain date. The DSOH may be calculated forthe order date of the refill prescription or for the delivery date ofthe refill prescription. If the user were to adjust the delivery date ofthe refill prescription to a later date, the prescription deliveryscheduling device may warn the user if the DSOH of the previously filledprescription would fall below a threshold amount prior to the newdelivery date. When the DSOH of a prescription falls below the thresholdamount, there is a risk that any delay in the user obtaining the refillcould result in a gap in care (missing one or more doses of theprescription).

In various implementations, the prescription delivery scheduling devicealso prevents the user from scheduling a refill prescription too early.For example, business rules may prevent certain drugs from beingrefilled too close to the most recent fill of the same prescription. Forexample, these business rules may be established according to federal,state, and local regulations, insurance plan requirements, PBMrequirements, drug manufacturer guidelines, doctor directives, etc.

Therefore, if the user is adjusting the delivery date of a refillprescription, the prescription delivery scheduling device can calculatean earliest possible delivery date of the refill prescription based on aprior fill and a present date. The prescription delivery schedulingdevice may then instruct the prescription delivery calendar to visiblyblock out all dates prior to the earliest possible delivery date of therefill prescription. In various implementations, the prescriptiondelivery scheduling device will prevent the user from dragging anddropping the refill prescription to a date prior to the earliestpossible delivery date of the refill prescription.

The prescription delivery calendar provides the user with the ability tosimply and efficiently adjust delivery dates of their prescriptionswithin the requirements and regulations of an operator of theprescription delivery scheduling device, such as the PBM, without havingto parse fine print or research refill rules. The prescription deliverycalendar further allows the user to log in to their account to determinewhen prescriptions will be delivered, giving the user more autonomy andreducing a number of calls to the PBM inquiring as to the deliverystatus of a prescription.

The prescription delivery calendar further provides an optimizationtechnique to reduce the number of days on which the user receivesprescription deliveries and to reduce the total number of deliveriesreceived. This creates efficiencies for the user, especially insituations where the user may need to be home to accept deliveries andin situations where the location of deliveries is less convenient (forexample, at a central office of an apartment complex).

The optimization technique bundles scheduled prescriptions within apredetermined time of one another to a single delivery date. Forexample, if, during the same week, a prescription is scheduled to bedelivered on Monday, Wednesday, and Friday, the optimization techniquemay allow all of the scheduled prescriptions to be adjusted to a singledelivery date, such as Monday. In fact, the scheduled prescriptions mayeven arrive in a single package. When bundling is requested, theprescription delivery scheduling device determines whether a selectedscheduled prescription can be moved to a nearby delivery date based on(i) an ability to fill the prescription by an assigned pharmacy to meetthe nearby delivery date, (ii) the DSOH of the selected scheduledprescription, and (iii) whether adjusting the delivery date would resultin refilling the selected scheduled prescription too soon.

High-Volume Pharmacy

FIG. 1 is a block diagram of an example implementation of a system 100for a high-volume pharmacy. While the system 100 is generally describedas being deployed in a high-volume pharmacy or a fulfillment center (forexample, a mail order pharmacy, a direct delivery pharmacy, etc.), thesystem 100 and/or components of the system 100 may otherwise be deployed(for example, in a lower-volume pharmacy, etc.). A high-volume pharmacymay be a pharmacy that is capable of filling at least some prescriptionsmechanically. The system 100 may include a benefit manager device 102and a pharmacy device 106 in communication with each other directlyand/or over a network 104. The system 100 may also include a storagedevice 110.

The benefit manager device 102 is a device operated by an entity that isat least partially responsible for creation and/or management of thepharmacy or drug benefit. While the entity operating the benefit managerdevice 102 is typically a pharmacy benefit manager (PBM), other entitiesmay operate the benefit manager device 102 on behalf of themselves orother entities (such as PBMs). For example, the benefit manager device102 may be operated by a health plan, a retail pharmacy chain, a drugwholesaler, a data analytics or other type of software-related company,etc. In some implementations, a PBM that provides the pharmacy benefitmay provide one or more additional benefits including a medical orhealth benefit, a dental benefit, a vision benefit, a wellness benefit,a radiology benefit, a pet care benefit, an insurance benefit, a longterm care benefit, a nursing home benefit, etc. The PBM may, in additionto its PBM operations, operate one or more pharmacies. The pharmaciesmay be retail pharmacies, mail order pharmacies, etc.

Some of the operations of the PBM that operates the benefit managerdevice 102 may include the following activities and processes. A member(or a person on behalf of the member) of a pharmacy benefit plan mayobtain a prescription drug at a retail pharmacy location (e.g., alocation of a physical store) from a pharmacist or a pharmacisttechnician. The member may also obtain the prescription drug throughmail order drug delivery from a mail order pharmacy location, such asthe system 100. In some implementations, the member may obtain theprescription drug directly or indirectly through the use of a machine,such as a kiosk, a vending unit, a mobile electronic device, or adifferent type of mechanical device, electrical device, electroniccommunication device, and/or computing device. Such a machine may befilled with the prescription drug in prescription packaging, which mayinclude multiple prescription components, by the system 100. Thepharmacy benefit plan is administered by or through the benefit managerdevice 102.

The member may have a copayment for the prescription drug that reflectsan amount of money that the member is responsible to pay the pharmacyfor the prescription drug. The money paid by the member to the pharmacymay come from, as examples, personal funds of the member, a healthsavings account (HSA) of the member or the member’s family, a healthreimbursement arrangement (HRA) of the member or the member’s family, ora flexible spending account (FSA) of the member or the member’s family.In some instances, an employer of the member may directly or indirectlyfund or reimburse the member for the copayments.

The amount of the copayment required by the member may vary acrossdifferent pharmacy benefit plans having different plan sponsors orclients and/or for different prescription drugs. The member’s copaymentmay be a flat copayment (in one example, $10), coinsurance (in oneexample, 10%), and/or a deductible (for example, responsibility for thefirst $500 of annual prescription drug expense, etc.) for certainprescription drugs, certain types and/or classes of prescription drugs,and/or all prescription drugs. The copayment may be stored in thestorage device 110 or determined by the benefit manager device 102.

In some instances, the member may not pay the copayment or may only paya portion of the copayment for the prescription drug. For example, if ausual and customary cost for a generic version of a prescription drug is$4, and the member’s flat copayment is $20 for the prescription drug,the member may only need to pay $4 to receive the prescription drug. Inanother example involving a worker’s compensation claim, no copaymentmay be due by the member for the prescription drug.

In addition, copayments may also vary based on different deliverychannels for the prescription drug. For example, the copayment forreceiving the prescription drug from a mail order pharmacy location maybe less than the copayment for receiving the prescription drug from aretail pharmacy location.

In conjunction with receiving a copayment (if any) from the member anddispensing the prescription drug to the member, the pharmacy submits aclaim to the PBM for the prescription drug. After receiving the claim,the PBM (such as by using the benefit manager device 102) may performcertain adjudication operations including verifying eligibility for themember, identifying/reviewing an applicable formulary for the member todetermine any appropriate copayment, coinsurance, and deductible for theprescription drug, and performing a drug utilization review (DUR) forthe member. Further, the PBM may provide a response to the pharmacy (forexample, the pharmacy system 100) following performance of at least someof the aforementioned operations.

As part of the adjudication, a plan sponsor (or the PBM on behalf of theplan sponsor) ultimately reimburses the pharmacy for filling theprescription drug when the prescription drug was successfullyadjudicated. The aforementioned adjudication operations generally occurbefore the copayment is received and the prescription drug is dispensed.However in some instances, these operations may occur simultaneously,substantially simultaneously, or in a different order. In addition, moreor fewer adjudication operations may be performed as at least part ofthe adjudication process.

The amount of reimbursement paid to the pharmacy by a plan sponsorand/or money paid by the member may be determined at least partiallybased on types of pharmacy networks in which the pharmacy is included.In some implementations, the amount may also be determined based onother factors. For example, if the member pays the pharmacy for theprescription drug without using the prescription or drug benefitprovided by the PBM, the amount of money paid by the member may behigher than when the member uses the prescription or drug benefit. Insome implementations, the amount of money received by the pharmacy fordispensing the prescription drug and for the prescription drug itselfmay be higher than when the member uses the prescription or drugbenefit. Some or all of the foregoing operations may be performed byexecuting instructions stored in the benefit manager device 102 and/oran additional device.

Examples of the network 104 include a Global System for MobileCommunications (GSM) network, a code division multiple access (CDMA)network, 3rd Generation Partnership Project (3GPP), an Internet Protocol(IP) network, a Wireless Application Protocol (WAP) network, or an IEEE802.11 standards network, as well as various combinations of the abovenetworks. The network 104 may include an optical network. The network104 may be a local area network or a global communication network, suchas the Internet. In some implementations, the network 104 may include anetwork dedicated to prescription orders: a prescribing network such asthe electronic prescribing network operated by Surescripts of Arlington,Virginia.

Moreover, although the system shows a single network 104, multiplenetworks can be used. The multiple networks may communicate in seriesand/or parallel with each other to link the devices 102-110.

The pharmacy device 106 may be a device associated with a retailpharmacy location (e.g., an exclusive pharmacy location, a grocery storewith a retail pharmacy, or a general sales store with a retail pharmacy)or other type of pharmacy location at which a member attempts to obtaina prescription. The pharmacy may use the pharmacy device 106 to submitthe claim to the PBM for adjudication.

Additionally, in some implementations, the pharmacy device 106 mayenable information exchange between the pharmacy and the PBM. Forexample, this may allow the sharing of member information such as drughistory that may allow the pharmacy to better service a member (forexample, by providing more informed therapy consultation and druginteraction information). In some implementations, the benefit managerdevice 102 may track prescription drug fulfillment and/or otherinformation for users that are not members, or have not identifiedthemselves as members, at the time (or in conjunction with the time) inwhich they seek to have a prescription filled at a pharmacy.

The pharmacy device 106 may include a pharmacy fulfillment device 112,an order processing device 114, and a pharmacy management device 116 incommunication with each other directly and/or over the network 104. Theorder processing device 114 may receive information regarding fillingprescriptions and may direct an order component to one or more devicesof the pharmacy fulfillment device 112 at a pharmacy. The pharmacyfulfillment device 112 may fulfill, dispense, aggregate, and/or pack theorder components of the prescription drugs in accordance with one ormore prescription orders directed by the order processing device 114.

In general, the order processing device 114 is a device located withinor otherwise associated with the pharmacy to enable the pharmacyfulfilment device 112 to fulfill a prescription and dispenseprescription drugs. In some implementations, the order processing device114 may be an external order processing device separate from thepharmacy and in communication with other devices located within thepharmacy.

For example, the external order processing device may communicate withan internal pharmacy order processing device and/or other deviceslocated within the system 100. In some implementations, the externalorder processing device may have limited functionality (e.g., asoperated by a user requesting fulfillment of a prescription drug), whilethe internal pharmacy order processing device may have greaterfunctionality (e.g., as operated by a pharmacist).

The order processing device 114 may track the prescription order as itis fulfilled by the pharmacy fulfillment device 112. The prescriptionorder may include one or more prescription drugs to be filled by thepharmacy. The order processing device 114 may make pharmacy routingdecisions and/or order consolidation decisions for the particularprescription order. The pharmacy routing decisions include whatdevice(s) in the pharmacy are responsible for filling or otherwisehandling certain portions of the prescription order. The orderconsolidation decisions include whether portions of one prescriptionorder or multiple prescription orders should be shipped together for auser or a user family. The order processing device 114 may also trackand/or schedule literature or paperwork associated with eachprescription order or multiple prescription orders that are beingshipped together. In some implementations, the order processing device114 may operate in combination with the pharmacy management device 116.

The order processing device 114 may include circuitry, a processor, amemory to store data and instructions, and communication functionality.The order processing device 114 is dedicated to performing processes,methods, and/or instructions described in this application. Other typesof electronic devices may also be used that are specifically configuredto implement the processes, methods, and/or instructions described infurther detail below.

In some implementations, at least some functionality of the orderprocessing device 114 may be included in the pharmacy management device116. The order processing device 114 may be in a client-serverrelationship with the pharmacy management device 116, in a peer-to-peerrelationship with the pharmacy management device 116, or in a differenttype of relationship with the pharmacy management device 116. The orderprocessing device 114 and/or the pharmacy management device 116 maycommunicate directly (for example, such as by using a local storage)and/or through the network 104 (such as by using a cloud storageconfiguration, software as a service, etc.) with the storage device 110.

The storage device 110 may include: non-transitory storage (for example,memory, hard disk, CD-ROM, etc.) in communication with the benefitmanager device 102 and/or the pharmacy device 106 directly and/or overthe network 104. The non-transitory storage may store order data 118,member data 120, claims data 122, drug data 124, prescription data 126,and/or plan sponsor data 128. Further, the system 100 may includeadditional devices, which may communicate with each other directly orover the network 104.

The order data 118 may be related to a prescription order. The orderdata may include type of the prescription drug (for example, drug nameand strength) and quantity of the prescription drug. The order data 118may also include data used for completion of the prescription, such asprescription materials. In general, prescription materials include anelectronic copy of information regarding the prescription drug forinclusion with or otherwise in conjunction with the fulfilledprescription. The prescription materials may include electronicinformation regarding drug interaction warnings, recommended usage,possible side effects, expiration date, date of prescribing, etc. Theorder data 118 may be used by a high-volume fulfillment center tofulfill a pharmacy order.

In some implementations, the order data 118 includes verificationinformation associated with fulfillment of the prescription in thepharmacy. For example, the order data 118 may include videos and/orimages taken of (i) the prescription drug prior to dispensing, duringdispensing, and/or after dispensing, (ii) the prescription container(for example, a prescription container and sealing lid, prescriptionpackaging, etc.) used to contain the prescription drug prior todispensing, during dispensing, and/or after dispensing, (iii) thepackaging and/or packaging materials used to ship or otherwise deliverthe prescription drug prior to dispensing, during dispensing, and/orafter dispensing, and/or (iv) the fulfillment process within thepharmacy. Other types of verification information such as barcode dataread from pallets, bins, trays, or carts used to transport prescriptionswithin the pharmacy may also be stored as order data 118.

The member data 120 includes information regarding the membersassociated with the PBM. The information stored as member data 120 mayinclude personal information, personal health information, protectedhealth information, etc. Examples of the member data 120 include name,address, telephone number, e-mail address, prescription drug history,etc. The member data 120 may include a plan sponsor identifier thatidentifies the plan sponsor associated with the member and/or a memberidentifier that identifies the member to the plan sponsor. The memberdata 120 may include a member identifier that identifies the plansponsor associated with the user and/or a user identifier thatidentifies the user to the plan sponsor. The member data 120 may alsoinclude dispensation preferences such as type of label, type of cap,message preferences, language preferences, etc.

The member data 120 may be accessed by various devices in the pharmacy(for example, the high-volume fulfillment center, etc.) to obtaininformation used for fulfillment and shipping of prescription orders. Insome implementations, an external order processing device operated by oron behalf of a member may have access to at least a portion of themember data 120 for review, verification, or other purposes.

In some implementations, the member data 120 may include information forpersons who are users of the pharmacy but are not members in thepharmacy benefit plan being provided by the PBM. For example, theseusers may obtain drugs directly from the pharmacy, through a privatelabel service offered by the pharmacy, the high-volume fulfillmentcenter, or otherwise. In general, the use of the terms “member” and“user” may be used interchangeably.

The claims data 122 includes information regarding pharmacy claimsadjudicated by the PBM under a drug benefit program provided by the PBMfor one or more plan sponsors. In general, the claims data 122 includesan identification of the client that sponsors the drug benefit programunder which the claim is made, and/or the member that purchased theprescription drug giving rise to the claim, the prescription drug thatwas filled by the pharmacy (e.g., the national drug code number, etc.),the dispensing date, generic indicator, generic product identifier (GPI)number, medication class, the cost of the prescription drug providedunder the drug benefit program, the copayment/coinsurance amount, rebateinformation, and/or member eligibility, etc. Additional information maybe included.

In some implementations, other types of claims beyond prescription drugclaims may be stored in the claims data 122. For example, medicalclaims, dental claims, wellness claims, or other types ofhealth-care-related claims for members may be stored as a portion of theclaims data 122.

In some implementations, the claims data 122 includes claims thatidentify the members with whom the claims are associated. Additionallyor alternatively, the claims data 122 may include claims that have beende-identified (that is, associated with a unique identifier but not witha particular, identifiable member).

The drug data 124 may include drug name (e.g., technical name and/orcommon name), other names by which the drug is known, activeingredients, an image of the drug (such as in pill form), etc. The drugdata 124 may include information associated with a single medication ormultiple medications.

The prescription data 126 may include information regardingprescriptions that may be issued by prescribers on behalf of users, whomay be members of the pharmacy benefit plan — for example, to be filledby a pharmacy. Examples of the prescription data 126 include user names,medication or treatment (such as lab tests), dosing information, etc.The prescriptions may include electronic prescriptions or paperprescriptions that have been scanned. In some implementations, thedosing information reflects a frequency of use (e.g., once a day, twicea day, before each meal, etc.) and a duration of use (e.g., a few days,a week, a few weeks, a month, etc.).

In some implementations, the order data 118 may be linked to associatedmember data 120, claims data 122, drug data 124, and/or prescriptiondata 126.

The plan sponsor data 128 includes information regarding the plansponsors of the PBM. Examples of the plan sponsor data 128 includecompany name, company address, contact name, contact telephone number,contact e-mail address, etc.

Fulfillment Device

FIG. 2 illustrates the pharmacy fulfillment device 112 according to anexample implementation. The pharmacy fulfillment device 112 may be usedto process and fulfill prescriptions and prescription orders. Afterfulfillment, the fulfilled prescriptions are packed for shipping.

The pharmacy fulfillment device 112 may include devices in communicationwith the benefit manager device 102, the order processing device 114,and/or the storage device 110, directly or over the network 104.Specifically, the pharmacy fulfillment device 112 may include palletsizing and pucking device(s) 206, loading device(s) 208, inspectdevice(s) 210, unit of use device(s) 212, automated dispensing device(s)214, manual fulfillment device(s) 216, review devices 218, imagingdevice(s) 220, cap device(s) 222, accumulation devices 224, packingdevice(s) 226, literature device(s) 228, unit of use packing device(s)230, and mail manifest device(s) 232. Further, the pharmacy fulfillmentdevice 112 may include additional devices, which may communicate witheach other directly or over the network 104.

In some implementations, operations performed by one of these devices206-232 may be performed sequentially, or in parallel with theoperations of another device as may be coordinated by the orderprocessing device 114. In some implementations, the order processingdevice 114 tracks a prescription with the pharmacy based on operationsperformed by one or more of the devices 206-232.

In some implementations, the pharmacy fulfillment device 112 maytransport prescription drug containers, for example, among the devices206-232 in the high-volume fulfillment center, by use of pallets. Thepallet sizing and pucking device 206 may configure pucks in a pallet. Apallet may be a transport structure for a number of prescriptioncontainers, and may include a number of cavities. A puck may be placedin one or more than one of the cavities in a pallet by the pallet sizingand pucking device 206. The puck may include a receptacle sized andshaped to receive a prescription container. Such containers may besupported by the pucks during carriage in the pallet. Different pucksmay have differently sized and shaped receptacles to accommodatecontainers of differing sizes, as may be appropriate for differentprescriptions.

The arrangement of pucks in a pallet may be determined by the orderprocessing device 114 based on prescriptions that the order processingdevice 114 decides to launch. The arrangement logic may be implementeddirectly in the pallet sizing and pucking device 206. Once aprescription is set to be launched, a puck suitable for the appropriatesize of container for that prescription may be positioned in a pallet bya robotic arm or pickers. The pallet sizing and pucking device 206 maylaunch a pallet once pucks have been configured in the pallet.

The loading device 208 may load prescription containers into the puckson a pallet by a robotic arm, a pick and place mechanism (also referredto as pickers), etc. In various implementations, the loading device 208has robotic arms or pickers to grasp a prescription container and moveit to and from a pallet or a puck. The loading device 208 may also printa label that is appropriate for a container that is to be loaded ontothe pallet, and apply the label to the container. The pallet may belocated on a conveyor assembly during these operations (e.g., at thehigh-volume fulfillment center, etc.).

The inspect device 210 may verify that containers in a pallet arecorrectly labeled and in the correct spot on the pallet. The inspectdevice 210 may scan the label on one or more containers on the pallet.Labels of containers may be scanned or imaged in full or in part by theinspect device 210. Such imaging may occur after the container has beenlifted out of its puck by a robotic arm, picker, etc., or may beotherwise scanned or imaged while retained in the puck. In someimplementations, images and/or video captured by the inspect device 210may be stored in the storage device 110 as order data 118.

The unit of use device 212 may temporarily store, monitor, label, and/ordispense unit of use products. In general, unit of use products areprescription drug products that may be delivered to a user or memberwithout being repackaged at the pharmacy. These products may includepills in a container, pills in a blister pack, inhalers, etc.Prescription drug products dispensed by the unit of use device 212 maybe packaged individually or collectively for shipping, or may be shippedin combination with other prescription drugs dispensed by other devicesin the high-volume fulfillment center.

At least some of the operations of the devices 206-232 may be directedby the order processing device 114. For example, the manual fulfillmentdevice 216, the review device 218, the automated dispensing device 214,and/or the packing device 226, etc. may receive instructions provided bythe order processing device 114.

The automated dispensing device 214 may include one or more devices thatdispense prescription drugs or pharmaceuticals into prescriptioncontainers in accordance with one or multiple prescription orders. Ingeneral, the automated dispensing device 214 may include mechanical andelectronic components with, in some implementations, software and/orlogic to facilitate pharmaceutical dispensing that would otherwise beperformed in a manual fashion by a pharmacist and/or pharmacisttechnician. For example, the automated dispensing device 214 may includehigh-volume fillers that fill a number of prescription drug types at arapid rate and blister pack machines that dispense and pack drugs into ablister pack. Prescription drugs dispensed by the automated dispensingdevices 214 may be packaged individually or collectively for shipping,or may be shipped in combination with other prescription drugs dispensedby other devices in the high-volume fulfillment center.

The manual fulfillment device 216 controls how prescriptions aremanually fulfilled. For example, the manual fulfillment device 216 mayreceive or obtain a container and enable fulfillment of the container bya pharmacist or pharmacy technician. In some implementations, the manualfulfillment device 216 provides the filled container to another devicein the pharmacy fulfillment devices 112 to be joined with othercontainers in a prescription order for a user or member.

In general, manual fulfillment may include operations at least partiallyperformed by a pharmacist or a pharmacy technician. For example, aperson may retrieve a supply of the prescribed drug, may make anobservation, may count out a prescribed quantity of drugs and place theminto a prescription container, etc. Some portions of the manualfulfillment process may be automated by use of a machine. For example,counting of capsules, tablets, or pills may be at least partiallyautomated (such as through use of a pill counter). Prescription drugsdispensed by the manual fulfillment device 216 may be packagedindividually or collectively for shipping, or may be shipped incombination with other prescription drugs dispensed by other devices inthe high-volume fulfillment center.

The review device 218 may process prescription containers to be reviewedby a pharmacist for proper pill count, exception handling, prescriptionverification, etc. Fulfilled prescriptions may be manually reviewedand/or verified by a pharmacist, as may be required by state or locallaw. A pharmacist or other licensed pharmacy person who may dispensecertain drugs in compliance with local and/or other laws may operate thereview device 218 and visually inspect a prescription container that hasbeen filled with a prescription drug. The pharmacist may review, verify,and/or evaluate drug quantity, drug strength, and/or drug interactionconcerns, or otherwise perform pharmacist services. The pharmacist mayalso handle containers which have been flagged as an exception, such ascontainers with unreadable labels, containers for which the associatedprescription order has been canceled, containers with defects, etc. Inan example, the manual review can be performed at a manual reviewstation.

The imaging device 220 may image containers once they have been filledwith pharmaceuticals. The imaging device 220 may measure a fill heightof the pharmaceuticals in the container based on the obtained image todetermine if the container is filled to the correct height given thetype of pharmaceutical and the number of pills in the prescription.Images of the pills in the container may also be obtained to detect thesize of the pills themselves and markings thereon. The images may betransmitted to the order processing device 114 and/or stored in thestorage device 110 as part of the order data 118.

The cap device 222 may be used to cap or otherwise seal a prescriptioncontainer. In some implementations, the cap device 222 may secure aprescription container with a type of cap in accordance with a userpreference (e.g., a preference regarding child resistance, etc.), a plansponsor preference, a prescriber preference, etc. The cap device 222 mayalso etch a message into the cap, although this process may be performedby a subsequent device in the high-volume fulfillment center.

The accumulation device 224 accumulates various containers ofprescription drugs in a prescription order. The accumulation device 224may accumulate prescription containers from various devices or areas ofthe pharmacy. For example, the accumulation device 224 may accumulateprescription containers from the unit of use device 212, the automateddispensing device 214, the manual fulfillment device 216, and the reviewdevice 218. The accumulation device 224 may be used to group theprescription containers prior to shipment to the member.

The literature device 228 prints, or otherwise generates, literature toinclude with each prescription drug order. The literature may be printedon multiple sheets of substrates, such as paper, coated paper, printablepolymers, or combinations of the above substrates. The literatureprinted by the literature device 228 may include information required toaccompany the prescription drugs included in a prescription order, otherinformation related to prescription drugs in the order, financialinformation associated with the order (for example, an invoice or anaccount statement), etc.

In some implementations, the literature device 228 folds or otherwiseprepares the literature for inclusion with a prescription drug order(e.g., in a shipping container). In other implementations, theliterature device 228 prints the literature and is separate from anotherdevice that prepares the printed literature for inclusion with aprescription order.

The packing device 226 packages the prescription order in preparationfor shipping the order. The packing device 226 may box, bag, orotherwise package the fulfilled prescription order for delivery. Thepacking device 226 may further place inserts (e.g., literature or otherpapers, etc.) into the packaging received from the literature device228. For example, bulk prescription orders may be shipped in a box,while other prescription orders may be shipped in a bag, which may be awrap seal bag.

The packing device 226 may label the box or bag with an address and arecipient’s name. The label may be printed and affixed to the bag orbox, be printed directly onto the bag or box, or otherwise associatedwith the bag or box. The packing device 226 may sort the box or bag formailing in an efficient manner (e.g., sort by delivery address, etc.).The packing device 226 may include ice or temperature sensitive elementsfor prescriptions that are to be kept within a temperature range duringshipping (for example, this may be necessary in order to retainefficacy). The ultimate package may then be shipped through postal mail,through a mail order delivery service that ships via ground and/or air(e.g., UPS, FEDEX, or DHL, etc.), through a delivery service, through alocker box at a shipping site (e.g., AMAZON locker or a PO Box, etc.),or otherwise.

The unit of use packing device 230 packages a unit of use prescriptionorder in preparation for shipping the order. The unit of use packingdevice 230 may include manual scanning of containers to be bagged forshipping to verify each container in the order. In an exampleimplementation, the manual scanning may be performed at a manualscanning station. The pharmacy fulfillment device 112 may also include amail manifest device 232 to print mailing labels used by the packingdevice 226 and may print shipping manifests and packing lists.

While the pharmacy fulfillment device 112 in FIG. 2 is shown to includesingle devices 206-232, multiple devices may be used. When multipledevices are present, the multiple devices may be of the same device typeor models, or may be a different device type or model. The types ofdevices 206-232 shown in FIG. 2 are example devices. In otherconfigurations of the system 100, lesser, additional, or different typesof devices may be included.

Moreover, multiple devices may share processing and/or memory resources.The devices 206-232 may be located in the same area or in differentlocations. For example, the devices 206-232 may be located in a buildingor set of adjoining buildings. The devices 206-232 may be interconnected(such as by conveyors), networked, and/or otherwise in contact with oneanother or integrated with one another (e.g., at the high-volumefulfillment center, etc.). In addition, the functionality of a devicemay be split among a number of discrete devices and/or combined withother devices.

FIG. 3 illustrates the order processing device 114 according to anexample implementation. The order processing device 114 may be used byone or more operators to generate prescription orders, make routingdecisions, make prescription order consolidation decisions, trackliterature with the system 100, and/or view order status and other orderrelated information. For example, the prescription order may becomprised of order components.

The order processing device 114 may receive instructions to fulfill anorder without operator intervention. An order component may include aprescription drug fulfilled by use of a container through the system100. The order processing device 114 may include an order verificationsubsystem 302, an order control subsystem 304, and/or an order trackingsubsystem 306. Other subsystems may also be included in the orderprocessing device 114.

The order verification subsystem 302 may communicate with the benefitmanager device 102 to verify the eligibility of the member and reviewthe formulary to determine appropriate copayment, coinsurance, anddeductible for the prescription drug and/or perform a DUR (drugutilization review). Other communications between the order verificationsubsystem 302 and the benefit manager device 102 may be performed for avariety of purposes.

The order control subsystem 304 controls various movements of thecontainers and/or pallets along with various filling functions duringtheir progression through the system 100. In some implementations, theorder control subsystem 304 may identify the prescribed drug in one ormore than one prescription orders as capable of being fulfilled by theautomated dispensing device 214. The order control subsystem 304 maydetermine which prescriptions are to be launched and may determine thata pallet of automated-fill containers is to be launched.

The order control subsystem 304 may determine that an automated-fillprescription of a specific pharmaceutical is to be launched and mayexamine a queue of orders awaiting fulfillment for other prescriptionorders, which will be filled with the same pharmaceutical. The ordercontrol subsystem 304 may then launch orders with similar automated-fillpharmaceutical needs together in a pallet to the automated dispensingdevice 214. As the devices 206-232 may be interconnected by a system ofconveyors or other container movement systems, the order controlsubsystem 304 may control various conveyors: for example, to deliver thepallet from the loading device 208 to the manual fulfillment device 216from the literature device 228, paperwork as needed to fill theprescription.

The order tracking subsystem 306 may track a prescription order duringits progress toward fulfillment. The order tracking subsystem 306 maytrack, record, and/or update order history, order status, etc. The ordertracking subsystem 306 may store data locally (for example, in a memory)or as a portion of the order data 118 stored in the storage device 110.

Referring back to FIG. 1 , a user device 108 may be used to access a webportal 130 to create an account with the user’s pharmacy or PBM andaccess a prescription delivery calendar that includes scheduledprescription deliveries of the user. The user device 108 may be adesktop computer, kiosk, or mobile computing device, such as a phone ortablet.

Calendar Interface

FIGS. 4A-4B are an example scheduling interface 400 depicting a calendarview of scheduled deliveries of prescription drugs for a particularuser. For example, the user may have an account through their pharmacyor PBM. Upon authenticating to the scheduling interface 400 using theiraccount, the scheduling interface 400 obtains the prescriptioninformation associated with the user’s account.

The scheduling interface 400 may be interactive, allowing the user toadjust scheduled prescription deliveries for delivery on a different dayusing, for example, a drag-and-drop operation. The drag-and-dropoperation may be performed by a cursor control device (such as a mouse)or directly on a display screen, such as with a finger or stylus. Newprescriptions can be scheduled and displayed on the scheduling interface400 once processed by the user’s PBM. For example, during typicalprocessing, once a new prescription is received, a prescription deliveryscheduling device may receive the new prescription and, once theprescription is scheduled for delivery, the prescription deliveryscheduling device may update the scheduling interface 400 to include thenew prescription on the corresponding scheduled delivery date.

The scheduling interface 400 displays monthly calendars 402-1 and 402-2,shown in FIG. 4A, and monthly calendars 402-3 and 402-4, shown in FIG.4B, with each scheduled prescription delivery listed on a scheduleddelivery date of the scheduled prescription. As shown, a scheduleddelivery 404 of Januvia brand tablets is scheduled for Aug. 29, 2018. Invarious implementations, each user’s account may include prescriptionsfor a set of individuals, such as a family under the same prescriptionbenefits program. FIG. 4A shows a set of individuals 406 named John,Jane, Billy, and Alice. To distinguish which prescription deliverycorresponds to which individual, each individual may have a particulargraphical signature, such as a color, shape, or symbol. In FIG. 4A, forexample, John has a star displayed next to his name. Therefore, anyscheduled delivery including a star, such as the scheduled delivery 404,corresponds to John.

The scheduling interface 400 may include a user interface (UI) elementfor each of the set of individuals that allows the displayed scheduleddeliveries to be narrowed to a proper subset of the set of individuals(such as a single individual). For example, in FIG. 4A, four buttons areshown, corresponding to the four individuals. Selecting the button forJohn causes all scheduled deliveries for individuals other than John tobe hidden. In other implementations, selecting the button for John mayalternately show and hide the scheduled deliveries for John—in otherwords, each of the four buttons would act as a toggle.

A set of scheduled prescription deliveries 408 is displayed on thescheduling interface 400. UI elements may allow the user to filter whatis being shown. For example, the scheduling interface 400 includes year,month, week, and day buttons 410, allowing the user to filter the viewaccording to a time period. Additionally, a today button 412 allows theuser to, upon selection, view the scheduled prescription deliveries forthe present day. Forward and backward buttons 414 allow the user to viewa previous or next screen of scheduled prescription deliveries (such asan adjacent pare of months).

The scheduling interface 400 includes a schedule optimization button 416that, upon selection, optimizes the scheduling of prescriptiondeliveries by attempting to reduce the number of days that prescriptionswill be delivered, also referred to as bundling. A view customizationbutton 418 allows the user to provide a custom date range as well asselect which individuals and prescriptions the user desires to view. Aclear selection button 420 resets the calendar view to a default view.For example, the default view may cover a predetermined time, such asfour months, and cause scheduled deliveries for all individuals to bevisible.

FIGS. 5A-5B are another view 430 of an example user interface. In FIG.5B, a scheduled delivery 432 (in this case, Januvia brand tabletsscheduled for Oct. 25, 2018) has been selected by a user. Upon userselection of the scheduled delivery 432, the interface displaysadditional information about the scheduled delivery 432 in aninformation box 434. For example, the information box 434 may includeone or more of a fill number, an amount of medication included in theorder, a prescribing physician, a delivery date, and a subsequentdelivery date for a refill of the scheduled delivery 432.

FIGS. 6A-6B are another view 440 of an example user interface followingdate bundling of scheduled deliveries. As described above and shown inFIG. 6A, the user may select the schedule optimization button 416 toadjust delivery dates of scheduled deliveries to reduce the number ofdelivery dates (and potentially, the number of delivered packages) forthe user. In FIGS. 4A-5B, a delivery of Pioglitazone was scheduled fordelivery on Sep. 3, 2018, a delivery of Vitamin D2 was scheduled forSeptember 4, a delivery of Zofran brand medication was scheduled forSeptember 21, a delivery of Bydureon brand medication was scheduled forSeptember 24, and a delivery of Atorvastatin was scheduled for September27.

After selection of the schedule optimization button 416, the scheduledprescription delivery system adjusts the delivery date of Vitamin D2earlier, into a first bundle 442 with Pioglitazone on September 3,reducing two days of deliveries to one. Similarly, the Bydureon deliveryand the Atorvastatin delivery are adjusted earlier to a second bundle444 to be delivered with Zofran on September 21. Similarly, a thirdbundle 446, including the same prescriptions as the second bundle 444,is created in November, reducing the total number of delivery dates inAugust through September from eleven to six.

The optimization mechanism is described in more detail below. In brief,one approach is for the scheduled prescription delivery system to firstattempt to move prescriptions scheduled within a predetermined window ofan earlier prescription to the earlier delivery date. For example, theAtorvastatin delivery day is moved to September 21 instead of the Zofrandelivery date being moved to September 27. In various implementations,the delivery dates may be adjusted to a later date based on an inability(such as due to pharmacy capacity or prescription rules) to move a dateearlier.

FIGS. 7A-7B are an example interface showing a delivery rescheduledclose to the present date. In this example, FIG. 7A shows that ascheduled delivery 452 of Januvia brand tablets has been adjustedearlier in time. However, when the earlier date is close to the presentdate, the system may not be able to guarantee this new delivery date.The system may therefore display some sort of warning or guidance, suchas a highlighted time frame 454 indicating a timeframe within which ascheduled delivery date is not guaranteed.

In various implementations, during a timeframe where rescheduling of aprescription delivery date is not guaranteed, the system may accept therescheduling request but will not guarantee a particular delivery date.For example, the system may reschedule the delivery date but may notindicate the rescheduled delivery date as a guaranteed date on theexample interface or otherwise. Instead, the system may maintain theoriginal guaranteed delivery date as the guaranteed delivery date.

In FIG. 7A, the highlighted time frame 454 is the last week in August.In various implementations, the interface may prevent reschedulingduring the highlighted time frame 454 or may display an alert inresponse to the delivery date of the scheduled delivery 452 beingadjusted to within the highlighted time frame 454. The highlighted timeframe 454 may be specific to each prescription — for example, based onthe inventory, packaging time, and shipping time for the pharmacyexpected to fulfill the prescription.

FIGS. 8A-8B are an example interface 460 depicting visually indicatingdates that are too soon to refill a prescription, such as when a user isperforming a drag-and-drop adjustment of a scheduled delivery. Invarious implementations, initiating a drag operation of a selectedprescription 462 (shown in FIG. 8B) by a user may result in theprescription delivery scheduling screen of the interface 460 determiningand then visually indicating the earliest possible refill date. Theinterface 460 may prevent the scheduled delivery from being placed priorto the earliest possible refill date. In various implementations, if theuser drops the scheduled delivery into a timeframe prior to the earliestpossible refill date, the interface 460 may then move the scheduleddelivery to the earliest possible refill date.

For example, while the user is dragging the scheduled delivery, a visualindication may be applied to all dates prior to the earliest possiblerefill date. This visual indication may include, as examples, one ormore of removing color (changing to grayscale), increasing transparencyof the date text, applying a black or grey fill, or applying a hatchedpattern.

As shown in FIG. 8A, the blocked-out dates 464 include all of August andSeptember. For example, the selected prescription 462 may be a refillprescription and, according to insurance and regulatory guidelines,certain prescriptions may not be refilled within a predetermined amountof time of the previously filled prescription of the same type.Therefore, the earliest possible refill date may be calculated based onsuch refill requirements to be October 1. Therefore, when the user isattempting to move the selected prescription 462 from an originaldelivery date of October 25 to a new delivery date (such as October 5),dates prior to October 1 are blocked out as indicated at 464.

FIGS. 9A-9B are an example interface 470 depicting a scheduled deliveryconfirmation. In various implementations, when the user reschedules ascheduled delivery, a confirmation dialog 472 may prompt the user toconfirm the rescheduling of the delivery date. This reduces the risk ofinadvertent rescheduling while viewing upcoming prescription deliveries.In FIG. 9B, the user has dragged-and-dropped a scheduled delivery (inthis case, Januvia brand medication) from the previously scheduleddelivery date (October 25, indicated at 474) to a new delivery date(October 5, indicated at 476). In response to the user confirming thechange in the confirmation dialog 472 displayed in FIG. 9A, thescheduled delivery is updated to October 5. If the user cancels thechange, the scheduled delivery will remain scheduled for the originaldate of October 25.

In various implementations, the example interface may prompt the userwith a worry-free refill confirmation request. If the user opts toenroll in worry free refills, the system automatically confirmsprescription delivery dates for a number of refills included on theprescription. For example, if the prescription includes five refills,the system will automatically schedule prescription delivery dates foreach of the five refills. Additionally, if the user grants renewalrequest permissions to the system (also received via a prompt on theexample interface), the system will automatically prompt anadministrator to request a prescription renewal for the prescriptionwhen the user’s prescription and refills are nearing an end. That is,the administrator may contact the user’s physician to request anotherprescription to facilitate prescription renewal for the user when theuser’s prescription is ending. In various implementations, theadministrator may initiate prescription renewal early — for example,before a last prescription refill — to ensure the user’s supply of theprescription does not lapse.

Prescription Delivery Scheduling Device

FIG. 10 is a functional block diagram of an example implementation of adelivery scheduling device 132. In various implementations, theinterfaces described in FIGS. 4A-9B may be generated by the deliveryscheduling device 132. The delivery scheduling device 132 may receiverequests from the web portal 130 (shown in FIG. 1 ). For example, when aprescription is received by the PBM, a default delivery date isscheduled for the prescription. When the user accesses the web portal,they will see the default delivery date for the prescription.

In various implementations, the default delivery date may be assigned bythe delivery scheduling device 132 in response to a scheduling requestfrom the pharmacy device 106. In response to receiving the schedulingrequest, the delivery scheduling device 132 obtains prescriptionparameters of the prescription from the pharmacy device 106. Theprescription parameters may include drug information, such as drugidentification, dosage information, etc.; user identificationinformation, such as name, address, etc.; refill information, such asdelivery date of previously filled prescriptions of the same drug, etc.

Regardless of whether the delivery scheduling device 132 assigns adefault delivery date, the web portal may provide a delivery dateadjustment in response to user input, such as a drag-and-drop operation.For example, when the user is attempting to reschedule the delivery dateof a scheduled prescription, the web portal will transmit a requestalong with request parameters to the delivery scheduling device 132. Therequest may also be generated in response to a bundling request, as byselection of the schedule optimization button 416 (shown in FIGS.4A-9B).

Once the delivery scheduling device 132 receives a request, the deliveryscheduling device 132 obtains the request parameters as well as thecurrently scheduled prescription delivery date (which may be stored bythe pharmacy device 106). A fill ability determination module 504receives the request parameters, the prescription parameters, and thescheduled prescription delivery date. The request parameters mayindicate a type of request, such as an adjusted delivery date requestwhen the user is performing the drag-and-drop operation, a bundlingrequest when the user selects the schedule optimization button, etc.

In response to receiving a new prescription, uploaded to the web portalor obtained from the pharmacy device 106, the fill ability determinationmodule 504 obtains prescription parameters of the new prescription (suchas from the pharmacy device 106). Based on the prescription parameters,the fill ability determination module 504 calculates an earliestpossible fill date of the new prescription based on pharmacy capacity.From the earliest possible fill date, the fill ability determinationmodule 504 calculates an earliest possible delivery date, which istransmitted to a delivery date adjustment module 508.

As described below, the delivery date adjustment module 508 selects adelivery date that is the same as or later than the earliest possibledelivery date, and transmits the earliest possible delivery date toupdate the pharmacy and the web portal. In various implementations, thefill ability determination module 504 may default to select the earliestpossible delivery date. Alternatively, the fill ability determinationmodule 504 may attempt to set a delivery date that is a predeterminedamount of time from the original request (for example, two weeks). Then,the fill ability determination module 504 may attempt to determinewhether the default delivery date can be met.

In response to receiving the requested delivery date or an adjusteddelivery request, the fill ability determination module 504 determineswhether the prescription can be delivered on the requested deliverydate. For example, the fill ability determination module 504 determinesa required fill date based on the requested delivery date. If theprescription can be filled by the required fill date, then the fillability determination module 504 transmits the requested delivery dateto a delivery date adjustment module 508. Alternatively, if the fillability determination module 504 determines that the required fill datecannot be met, then the fill ability determination module 504 calculatesan earliest fill date. A fill ability is determined based onprescription processing times as well as drug stock and order capacityat an assigned fulfillment pharmacy. Based on the earliest fill date,the fill ability determination module 504 calculates an earliestdelivery date and forwards the earliest delivery date along with therequested delivery date to the delivery date adjustment module 508.

An inventory determination module 512 receives the request parameters,the prescription parameters, and the scheduled delivery date. Inresponse to receiving the adjusted delivery date request and, based onthe prescription parameters, the inventory determination module 512determines whether the prescription is a refill prescription. If theprescription is a refill prescription, the inventory determinationmodule 512 calculates a day supply on hand (DSOH) of the prescription.The inventory determination module 512 determines when the user receivedthe most recent refill of the prescription and calculates, assuming 100%adherence, an amount of drug doses remaining in the user’s possession(or, equivalently, DSOH). In various implementations, the inventorydetermination module 512 determines the DSOH only based on the mostrecent refill prescription receipt date and a stated duration of theprescription. In various implementations, the inventory determinationmodule 512 may consider all past refill prescriptions to calculate theDSOH, assuming 100% adherence.

The inventory determination module 512 transmits the DSOH to thedelivery date adjustment module 508 and an alert generation module 516.In response to the DSOH being less than or equal to a threshold amount,the alert generation module 516 transmits a DSOH warning to the webportal. For example, if delivering the prescription on the requesteddelivery date results in the user having, by the delivery day, a numberof doses less than or equal to the threshold amount, the DSOH warning istransmitted to the web portal to warn the user.

The delivery date adjustment module 508 receives the requested deliverydate and an approved delivery date from the fill ability determinationmodule 504 as well as the DSOH from the inventory determination module512. The delivery date adjustment module 508 determines whether therequested delivery date needs to be adjusted based on whether theapproved delivery date deviates from the requested delivery date. If theapproved delivery date deviates from the requested delivery date, thedelivery date adjustment module 508 transmits a notification request toa delivery date notification module 520 along with the approved deliverydate.

The delivery date notification module 520 generates a notificationincluding the approved delivery date and transmits the notificationincluding the approved delivery date to the web portal for display tothe user. The delivery date adjustment module 508 also transmits theapproved delivery date to a delivery date update module 524. Thedelivery date update module 524 also receives the request parameters anddetermines whether the delivery date was adjusted. In response todetermining that the delivery date was adjusted, the delivery dateupdate module 524 transmits the updated delivery date to the pharmacydevice 106. When the approved delivery date does not deviate from therequested delivery date, the delivery date adjustment module 508 doesnot transmit the notification request to the delivery date notificationmodule 520 and the delivery date update module 524 does not update thepharmacy device 106.

A block-out determination module 528 receives request parameters,prescription parameters, and the scheduled delivery date. If the requestparameters include an indication the user is performing a drag-and-dropoperation for the prescription using the web portal, the block-outdetermination module 528 identifies if the prescription is a refillbased on the prescription parameters. If the prescription is not arefill, the block-out determination module 528 sends a present date to ablock-out module 532. In various implementations, the block-outdetermination module 528 may, in response to the prescription not beinga refill, calculate an earliest possible fill date of the prescriptionaccording to pharmacy capacity, the present date, etc. Based on theearliest possible fill date of the prescription, the block-outdetermination module 528 may calculate an earliest possible deliverydate of the prescription. In this case, the block-out determinationmodule 528 transmits the later of the earliest possible delivery date ofthe prescription and the present date to the block-out module 532.

If the block-out determination module 528 determines that theprescription is a refill, then the block-out determination module 528determines the earliest possible fill date of the prescription based ona most recent fill date of a most recent refill. As described above, anumber of prescriptions may only be refilled a predetermined delay afterthe user has received the most recent refill. For example, prescriptionsmay not be refilled too early based on insurance requirements as well asdrug regulations. In various implementations, once the earliest possiblefill date of the prescription is determined based on a most recentrefill delivery date of the same drug, the block-out determinationmodule 528 calculates an earliest possible delivery date based on theearliest possible fill date. The earliest possible delivery date is thenforwarded to the block-out module 532.

Additionally or alternatively, the block-out determination module 528,as mentioned above, may calculate the earliest possible fill date basedon capacity, such as pharmacy capacity, as described above, when theprescription is not a refill prescription. From the earliest possiblefill date based on capacity, the earliest possible delivery date isdetermined. The block-out determination module 528 may then transmit thelater of the following dates: the earliest possible delivery date basedon the most recent refill delivery date, the earliest possible deliverydate based on capacity, and the present date.

Based on the earliest possible delivery day, the block-out module 532allows the web portal to visibly block out each date prior to theearliest possible delivery date. These dates are blocked out to visiblydepict to the user that these dates are unavailable. In variousimplementations, the web portal does not allow the selected prescriptionto be moved to one of the blocked out dates established by the block-outmodule 532.

A bundling module 536 receives request parameters and, in response tothe request parameters including a bundling request (such as, when theschedule optimization button is selected), the bundling module 536obtains prescription parameters and scheduled prescription deliverydates according to a specified date range included in the requestparameters. Then, the bundling module 536 adjusts the delivery dates ofscheduled prescriptions within the specified date range to minimize thenumber of delivery dates. For example, one bundling approach isdescribed in FIGS. 13A-13B.

In various implementations, the bundling module 536 will identify, forexample, one week within the specified date range and determine if ascheduled prescription delivered later in the week can be adjusted to ascheduled prescription delivered earlier in the week. The bundlingmodule 536 considers DSOH as well as factors similar to those describedabove with respect to an earliest possible fill date of prescriptions.If any scheduled prescriptions are bundled, the bundling module 536transmits the new delivery dates associated with bundled prescriptionsto the delivery date update module 524. The delivery date update module524 updates any necessary delivery dates by sending adjusted deliverydates to the pharmacy device 106.

Flowcharts

FIG. 11 is a flowchart of example prescription delivery date scheduling.Control begins upon receiving a prescription order. At 604, controlobtains prescription parameters and a requested delivery date. Controlcontinues to 608, where control determines an earliest possibleprescription fill date. Control continues to 612 to determine whetherthe prescription order includes a requested delivery date. If not,control proceeds to 616 to determine an earliest possible delivery dateof the prescription based on the earliest possible fill date; otherwise,control continues to 620, where control determines a required fill dateto deliver the prescription on the requested delivery date.

At 624, control compares the required fill date and the earliestpossible prescription filled date. If control determines that therequired fill date is too early, control continues to 616 to determinethe earliest possible delivery date of the prescription based on theearliest possible fill date. At 628, control sets a prescriptiondelivery date to the determined earliest possible delivery date. Controlcontinues to 632 to notify the user of the prescription delivery date.Control then proceeds to 636 to estimate the DSOH of the prescription asof the prescription delivery date.

If, at 624, the determined required fill date is not too early, controlcontinues to 640, sets the prescription delivery date to the requesteddelivery date, and proceeds to 636. As described above, the DSOH isrelevant when the prescription is a refill. The DSOH indicates thenumber of days of doses remaining with the user from the most recentlyfilled prescription.

Control continues from 636 to 644 to determine whether the DSOH isgreater than or equal to a threshold amount. If no, control proceeds to648, where control generates an alert that the DSOH will be less thanthe threshold amount. Control then continues to 652, transmits thealert, and continues to 656. However, if at 644, the DSOH is greaterthan or equal to the threshold amount, control continues to 656. At 656,control notifies the user of the prescription delivery date and thenends. Notification of the user may take the form of a message in the webportal or a visual indication of a delivery date.

FIG. 12 is a flowchart of example delivery date block-out. Controlbegins at 704 upon a user selecting a scheduled delivery, which mayindicate the beginning of, or the potential for, a drag-and-dropoperation. At 704, control obtains prescription parameters and a presentdelivery date. Control continues to 708, where control determines anearliest possible fill date based on a prior fill date. At 712, controldetermines an earliest possible delivery date based on the earliestpossible fill date. Control continues to 716 to generate block-out dateinformation, including dates prior to the determined earliest possibledelivery date. As described above, control calculates the earliestpossible delivery date of the prescription based on a prior fill date,pharmacy capacity, and a present date.

At 720, during the user interface drag operation, control visibly blocksdisplayed dates according to the block-out date information. Forexample, the user interface grays out or prevents selection of datesprior to the earliest possible delivery date while the scheduledprescription is being dragged. In addition, control may prevent thedelivery date of the scheduled prescription from being adjusted to adate prior to the earliest possible delivery date.

FIGS. 13A-13B together form a flowchart of example prescription deliverydate bundling. Control begins upon receiving a bundle request. At 804,control obtains a set of prescriptions currently scheduled within aspecified date range, such as one month from the present date. Controlcontinues to 808, where control designates a prescription within the setof prescriptions that has the earliest scheduled delivery date as ananchor prescription. Control continues to 812 and sets a target deliverydate to a scheduled delivery date of the anchor prescription. Then, at816, control determines whether additional prescription deliveries arescheduled within a predetermined time of the target delivery date. Forexample, the predetermined time may be one week. In other words, whenthe predetermined time is one week, control determines whetheradditional prescription deliveries are scheduled within one week priorto and one week subsequent to the target delivery date.

If no additional prescription deliveries are scheduled within thepredetermined time, control proceeds to 820 to designate a prescriptionwith the next scheduled delivery date after the target delivery date asthe anchor prescription and returns to 812. The anchor prescription isupdated if no additional prescription deliveries are scheduled withinthe predetermined time of the target delivery date because onlyprescriptions near one another are bundled, preventing control fromattempting to bundle prescriptions that are months apart.

If, at 816, additional prescription deliveries are scheduled within thepredetermined time, control proceeds to 824. At 824, control creates abundle list including each prescription scheduled for delivery withinthe predetermined time of the target delivery date but excludingprescriptions on the target delivery date. The bundle list representsthe scheduled prescriptions that control will attempt to adjust to thetarget delivery date.

Control proceeds to 828 to select a first prescription in the bundlelist as a candidate prescription. At 832, control obtains prescriptionparameters for the candidate prescription. As mentioned previously,prescription parameters may be obtained from the pharmacy device 106described in FIG. 1 . Control continues to 836 to determine a requiredfill date to deliver the candidate prescription on the target deliverydate. At 840, control determines if the required fill date is too closeto a prior fill date. In certain circumstances (for example, accordingto insurance or drug regulations) certain prescriptions may be requiredto be filled a predetermined amount of days apart from one another.

Therefore, if the required fill date is too close to the prior fill dateat 840, control proceeds to 844 to determine an earliest possible filldate of the candidate prescription. Then, control proceeds to 848 todetermine a delivery date of the candidate prescription based on theearliest possible fill date. At 852, control sets the target deliverydate to the determined delivery date. Therefore, if moving the candidateprescription to the target delivery date results in the candidateprescription being filled too early, control adjusts the target deliverydate to the presently scheduled delivery date of the candidateprescription. This represents an attempt to bundle the prescriptionsscheduled within a predetermined time of the candidate prescription tothe presently scheduled delivery date of the candidate prescription.Control then returns to 824. Otherwise, if at 840 the required fill dateis not too close to the prior fill date, control proceeds to 856 of FIG.13B.

In FIG. 13B, at 856, control determines if the presently scheduleddelivery date of the candidate prescription is earlier than the targetdelivery date. If so, control proceeds to 864; otherwise, controlcontinues to 860. At 864, control determines a DSOH of the candidateprescription as of the target delivery date. At 868, if the determinedDSOH of the candidate prescription is greater than or equal to thethreshold amount, control proceeds to 860. Otherwise, if the DSOH isequal to or below the threshold amount, control proceeds to 872. At 872,control removes the candidate prescription from the bundle list andcontinues at 874.

At 860, control adjusts the presently scheduled delivery date of thecandidate prescription to the target delivery date. Then, controlproceeds to 874 to determine if another prescription is in the bundlelist. If the bundle list includes another prescription, control returnsto 878 in FIG. 13A; otherwise, if the bundle list does not includeanother prescription, control continues to 882. At 882, controldetermines if another prescription is in the set of prescriptions andscheduled for delivery after the target delivery date. If not, thencontrol has already attempted to bundle all possible groups scheduled inthe specified date range and control ends. Otherwise, if anotherprescription is in the set of prescriptions and is scheduled fordelivery after the target delivery date, control returns to 820 in FIG.13A.

Returning to FIG. 13A, at 820 control designates the prescription withthe next scheduled delivery date after the target delivery date as theanchor prescription. Control then continues at 812. At 878, controlselects the next prescription in the bundle list as the candidateprescription and continues at 832 to obtain the relevant prescriptionparameters.

Conclusion

The foregoing description is merely illustrative in nature and is in noway intended to limit the disclosure, its application, or uses. Thebroad teachings of the disclosure can be implemented in a variety offorms. Therefore, while this disclosure includes particular examples,the true scope of the disclosure should not be so limited since othermodifications will become apparent upon a study of the drawings, thespecification, and the following claims. It should be understood thatone or more steps within a method may be executed in different order (orconcurrently) without altering the principles of the present disclosure.Further, although each of the embodiments is described above as havingcertain features, any one or more of those features described withrespect to any embodiment of the disclosure can be implemented in and/orcombined with features of any of the other embodiments, even if thatcombination is not explicitly described. In other words, the describedembodiments are not mutually exclusive, and permutations of one or moreembodiments with one another remain within the scope of this disclosure.

Spatial and functional relationships between elements (for example,between modules) are described using various terms, including“connected,” “engaged,” “interfaced,” and “coupled.” Unless explicitlydescribed as being “direct,” when a relationship between first andsecond elements is described in the above disclosure, that relationshipencompasses a direct relationship where no other intervening elementsare present between the first and second elements, and also an indirectrelationship where one or more intervening elements are present (eitherspatially or functionally) between the first and second elements. Asused herein, the phrase at least one of A, B, and C should be construedto mean a logical (A OR B OR C), using a non-exclusive logical OR, andshould not be construed to mean “at least one of A, at least one of B,and at least one of C.”

In the figures, the direction of an arrow, as indicated by thearrowhead, generally demonstrates the flow of information (such as dataor instructions) that is of interest to the illustration. For example,when element A and element B exchange a variety of information butinformation transmitted from element A to element B is relevant to theillustration, the arrow may point from element A to element B. Thisunidirectional arrow does not imply that no other information istransmitted from element B to element A. Further, for information sentfrom element A to element B, element B may send requests for, or receiptacknowledgements of, the information to element A. The term subset doesnot necessarily require a proper subset. In other words, a first subsetof a first set may be coextensive with (equal to) the first set.

In this application, including the definitions below, the term “module”or the term “controller” may be replaced with the term “circuit.” Theterm “module” may refer to, be part of, or include processor hardware(shared, dedicated, or group) that executes code and memory hardware(shared, dedicated, or group) that stores code executed by the processorhardware.

The module may include one or more interface circuits. In some examples,the interface circuit(s) may implement wired or wireless interfaces thatconnect to a local area network (LAN) or a wireless personal areanetwork (WPAN). Examples of a LAN are Institute of Electrical andElectronics Engineers (IEEE) Standard 802.11-2016 (also known as theWIFI wireless networking standard) and IEEE Standard 802.3-2015 (alsoknown as the ETHERNET wired networking standard). Examples of a WPAN arethe BLUETOOTH wireless networking standard from the Bluetooth SpecialInterest Group and IEEE Standard 802.15.4.

The module may communicate with other modules using the interfacecircuit(s). Although the module may be depicted in the presentdisclosure as logically communicating directly with other modules, invarious implementations the module may actually communicate via acommunications system. The communications system includes physicaland/or virtual networking equipment such as hubs, switches, routers, andgateways. In some implementations, the communications system connects toor traverses a wide area network (WAN) such as the Internet. Forexample, the communications system may include multiple LANs connectedto each other over the Internet or point-to-point leased lines usingtechnologies including Multiprotocol Label Switching (MPLS) and virtualprivate networks (VPNs).

In various implementations, the functionality of the module may bedistributed among multiple modules that are connected via thecommunications system. For example, multiple modules may implement thesame functionality distributed by a load balancing system. In a furtherexample, the functionality of the module may be split between a server(also known as remote, or cloud) module and a client (or, user) module.

The term code, as used above, may include software, firmware, and/ormicrocode, and may refer to programs, routines, functions, classes, datastructures, and/or objects. Shared processor hardware encompasses asingle microprocessor that executes some or all code from multiplemodules. Group processor hardware encompasses a microprocessor that, incombination with additional microprocessors, executes some or all codefrom one or more modules. References to multiple microprocessorsencompass multiple microprocessors on discrete dies, multiplemicroprocessors on a single die, multiple cores of a singlemicroprocessor, multiple threads of a single microprocessor, or acombination of the above.

Shared memory hardware encompasses a single memory device that storessome or all code from multiple modules. Group memory hardwareencompasses a memory device that, in combination with other memorydevices, stores some or all code from one or more modules.

The term memory hardware is a subset of the term computer-readablemedium. The term computer-readable medium, as used herein, does notencompass transitory electrical or electromagnetic signals propagatingthrough a medium (such as on a carrier wave); the term computer-readablemedium is therefore considered tangible and non-transitory. Non-limitingexamples of a non-transitory computer-readable medium are nonvolatilememory devices (such as a flash memory device, an erasable programmableread-only memory device, or a mask read-only memory device), volatilememory devices (such as a static random access memory device or adynamic random access memory device), magnetic storage media (such as ananalog or digital magnetic tape or a hard disk drive), and opticalstorage media (such as a CD, a DVD, or a Blu-ray Disc).

The apparatuses and methods described in this application may bepartially or fully implemented by a special purpose computer created byconfiguring a general purpose computer to execute one or more particularfunctions embodied in computer programs. The functional blocks andflowchart elements described above serve as software specifications,which can be translated into the computer programs by the routine workof a skilled technician or programmer.

The computer programs include processor-executable instructions that arestored on at least one non-transitory computer-readable medium. Thecomputer programs may also include or rely on stored data. The computerprograms may encompass a basic input/output system (BIOS) that interactswith hardware of the special purpose computer, device drivers thatinteract with particular devices of the special purpose computer, one ormore operating systems, user applications, background services,background applications, etc.

The computer programs may include: (i) descriptive text to be parsed,such as HTML (hypertext markup language), XML (extensible markuplanguage), or JSON (JavaScript Object Notation), (ii) assembly code,(iii) object code generated from source code by a compiler, (iv) sourcecode for execution by an interpreter, (v) source code for compilationand execution by a just-in-time compiler, etc. As examples only, sourcecode may be written using syntax from languages including C, C++, C#,Objective-C, Swift, Haskell, Go, SQL, R, Lisp, Java®, Fortran, Perl,Pascal, Curl, OCaml, Javascript®, HTML5 (Hypertext Markup Language 5threvision), Ada, ASP (Active Server Pages), PHP (PHP: HypertextPreprocessor), Scala, Eiffel, Smalltalk, Erlang, Ruby, Flash®, VisualBasic®, Lua, MATLAB, SIMULINK, and Python®.

What is claimed is:
 1. A system for generating dynamic user interfaces,the system comprising: memory hardware configured to store instructionsand processor hardware configured to execute the instructions, whereinthe instructions include: generating an interactive graphical userinterface having a plurality of fields, each field corresponding to oneof a plurality of dates, generating a selectable user interface elementat a first field of the plurality of fields, the first fieldcorresponding to a scheduled delivery date for a recipient, and inresponse to a user dragging-and-dropping the selectable user interfaceelement to a second field of the plurality of fields, the second fieldcorresponding to an adjusted delivery date for the recipient:calculating a supply measure of a prior fill remaining with therecipient based on a stated duration of the prior fill and a datecorresponding to receipt of the prior fill by the recipient, in responseto the supply measure being less than a threshold, outputting an errormessage to the interactive graphical user interface, and in response tothe supply measure being greater than the threshold, moving theselectable user interface element to the second field and updating thescheduled delivery date to be the adjusted delivery date.
 2. The systemof claim 1 wherein the instructions include calculating an earliestpossible delivery date for a refill prescription of the recipient inresponse to the user selecting the selectable user interface element. 3.The system of claim 2 wherein the instructions include, in response tothe adjusted delivery date being prior to the earliest possible deliverydate: moving the selectable user interface element to a third field ofthe plurality of fields, the third field corresponding to the earliestpossible delivery date and updating the scheduled delivery date to bethe earliest possible delivery date.
 4. The system of claim 3 whereinthe instructions include blocking out fields of the interactivegraphical user interface corresponding to dates prior to the earliestpossible delivery date.
 5. The system of claim 4 wherein theinstructions include blocking out fields of the interactive graphicaluser interface by applying a visual indication to the blocked-outfields.
 6. The system of claim 5 wherein the visual indication includesremoving color from the blocked-out fields.
 7. The system of claim 5wherein the visual indication includes increasing transparency of datetext associated with the blocked-out fields.
 8. The system of claim 5wherein the visual indication includes applying a black fill to theblocked-out fields.
 9. The system of claim 5 wherein the visualindication includes applying a grey fill to the blocked-out fields. 10.The system of claim 5 wherein the visual indication includes applying ahatched pattern to the blocked-out fields.
 11. A computerized method forgenerating dynamic user interfaces, the method comprising: generating aninteractive graphical user interface having a plurality of fields, eachfield corresponding to one of a plurality of dates; generating aselectable user interface element at a first field of the plurality offields, the first field corresponding to a scheduled delivery date for arecipient; and in response to a user dragging-and-dropping theselectable user interface element to a second field of the plurality offields, the second field corresponding to an adjusted delivery date forthe recipient: calculating a supply measure of a prior fill remainingwith the recipient based on a stated duration of the prior fill and adate corresponding to receipt of the prior fill by the recipient, inresponse to the supply measure being less than a threshold, outputtingan error message to the interactive graphical user interface, and inresponse to the supply measure being greater than the threshold, movingthe selectable user interface element to the second field and updatingthe scheduled delivery date to be the adjusted delivery date.
 12. Themethod of claim 11 further comprising calculating an earliest possibledelivery date for a refill prescription of the recipient in response tothe user selecting the selectable user interface element.
 13. The methodof claim 12 further comprising, in response to the adjusted deliverydate being prior to the earliest possible delivery date: moving theselectable user interface element to a third field of the plurality offields, the third field corresponding to the earliest possible deliverydate and updating the scheduled delivery date to be the earliestpossible delivery date.
 14. The method of claim 13 further comprisingblocking out fields of the interactive graphical user interfacecorresponding to dates prior to the earliest possible delivery date. 15.The method of claim 14 further comprising blocking out fields of theinteractive graphical user interface by applying a visual indication tothe blocked-out fields.
 16. The method of claim 15 wherein the visualindication includes removing color from the blocked-out fields.
 17. Themethod of claim 15 wherein the visual indication includes increasingtransparency of date text associated with the blocked-out fields. 18.The method of claim 15 wherein the visual indication includes applying ablack fill to the blocked-out fields.
 19. The method of claim 15 whereinthe visual indication includes applying a grey fill to the blocked-outfields.
 20. The method of claim 15 wherein the visual indicationincludes applying a hatched pattern to the blocked-out fields.